home *** CD-ROM | disk | FTP | other *** search
-
-
-
- tnmsgfmt(1) tnmsgfmt(1)
-
-
- NNAAMMEE
- tnmsgfmt - create message object files from portable
- object files
-
-
- LLOOCCAATTIIOONN
- TNHOME/usr/bin
-
-
- SSYYNNOOPPSSIISS
- tnmsgfmt [-v] _f_i_l_e.xmsg
-
-
- DDEESSCCRRIIPPTTIIOONN
- This command creates message object files from portable
- object files -- those with the ".xmsg" extension -- with-
- out changing the portable files. An ".xmsg" file contains
- messages displayed to users by system commands or applica-
- tion programs. You can edit these files and translate the
- messages to any language supported by the system.
-
- All ".xmsg" files have the same format. Each file con-
- tains one or more lines, and each line contains a comment
- or a statement. A comment begins with a hash mark (#)
- begins and ends with a new-line character. The "tnmsgfmt"
- command ignores all comments. Statements follow this for-
- mat:
-
- _d_i_r_e_c_t_i_v_e _v_a_l_u_e
-
- Each _d_i_r_e_c_t_i_v_e definition starts at the beginning of the
- line, and white space -- either a space or a tab character
- -- separates it from the _v_a_l_u_e definition. The _v_a_l_u_e vari-
- able consists of one or more quote-enclosed strings sepa-
- rated by white spaces. Use any of the following direc-
- tives:
-
- domain _d_o_m_a_i_n
- msgid _m_e_s_s_a_g_e___i_d_e_n_t_i_f_i_e_r
- msgstr _m_e_s_s_a_g_e___s_t_r_i_n_g
-
- For the "domain" directive, the value of _d_o_m_a_i_n should
- correspond to the message file name. For example, if you
- edit messages for the "tnnlc_lowutils" domain, the direc-
- tive should read "domain tnnlc_lowutils" and the output
- becomes the message file "tnnlc_lowutils.mo".
-
- The "msgid" directive specifies the value of a message
- identifier associated with the directive that follows it.
- The _m_e_s_s_a_g_e___i_d_e_n_t_i_f_i_e_r variable represents the target
- string to use at retrieval time. Follow each "msgid"
- directive statement with a "msgstr" directive statement.
- Do not change the "msgid" lines, since the code uses them
- as keys to locate the translated strings defined by the
-
-
-
- tas-ss-5.3.0 1998/06/17 1
-
-
-
-
-
- tnmsgfmt(1) tnmsgfmt(1)
-
-
- "msgstr" lines. Message strings for the _m_e_s_s_a_g_e___s_t_r_i_n_g
- variable can contain any of the following escape
- sequences:
-
- \n - new line
- \t - tab
- \v - vertical tab
- \b - backspace
- \r - carriage return
- \f - form feed
- \ - backslash
- \" - double quotes
- \ddd - octalbit pattern
- \xDD - hexadecimal bit pattern
-
-
- OOPPTTIIOONN
- -v List duplicate message identifiers without
- re-defining message strings.
-
-
- OOPPEERRAANNDD
- _f_i_l_e The name of the portable object file you
- created using the directives listed in the
- description above.
-
-
- EEXXAAMMPPLLEE
- To create a message object file from the portable object
- file "textfile.xmsg" and list duplicate message identi-
- fiers without re-defining message strings:
-
- tnmsgfmt -v textfile.xmsg
-
-
- SSEEEE AALLSSOO
- tncmnames(1), tngettext(1)
-
-
-
- NNOOTTEESS
- Install message object files in the directory "
- _T_N_H_O_M_E /usr/lib/locale_//_lm_as_ng_gs_[_/_c_h_a_r_s_e_t_/_]_"_, where _T_N_H_O_M_E
- represents the TotalNET home directory
- "/var/opt/totalnet" or, for AIX, "/var/totalnet".
- The _l_a_n_g variable represents the message language
- defined for the LC_MESSAGES environment variable or
- for the LANG environment variable, and _c_h_a_r_s_e_t rep-
- resents the message character set defined for the
- LC_CHARSET environment variable.
-
-
- Messages can have any length; however, each line in
- the ".xmsg" file can have no more than MAX_INPUT
-
-
-
- tas-ss-5.3.0 1998/06/17 2
-
-
-
-
-
- tnmsgfmt(1) tnmsgfmt(1)
-
-
- (512) bytes.
-
-
- Installing message catalogs in the C locale serves
- no purpose, since "tnmsgfmt" ignores them for the
- sake of efficiency.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- tas-ss-5.3.0 1998/06/17 3
-
-
-